Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 05b63396d7ba4073f3f2029b8cbc844cd085e7811fa535c81eb2b9abe1369fe8

Tx prefix hash: bd72a8b9e471d4a163743ba19fb65bb51a66451d15dc231b68f86fa0b0b0c583
Tx public key: a1064ab35abf02ea4af2984dc2293922590920e66d3c8083f6a7db3a61137513
Timestamp: 1635354133 Timestamp [UCT]: 2021-10-27 17:02:13 Age [y:d:h:m:s]: 03:201:18:10:19
Block: 361676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 922444 RingCT/type: yes/0
Extra: 01a1064ab35abf02ea4af2984dc2293922590920e66d3c8083f6a7db3a611375130211000000074f792ffd000000000000000000

1 output(s) for total of 38.870280947000 dcy

stealth address amount amount idx
00: 70adafaca1483ffbaac630554684569649797a03c7511f3c268e515e5bc3a6e3 38.870280947000 735734 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 361686, "vin": [ { "gen": { "height": 361676 } } ], "vout": [ { "amount": 38870280947, "target": { "key": "70adafaca1483ffbaac630554684569649797a03c7511f3c268e515e5bc3a6e3" } } ], "extra": [ 1, 161, 6, 74, 179, 90, 191, 2, 234, 74, 242, 152, 77, 194, 41, 57, 34, 89, 9, 32, 230, 109, 60, 128, 131, 246, 167, 219, 58, 97, 19, 117, 19, 2, 17, 0, 0, 0, 7, 79, 121, 47, 253, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8