Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85e069dac74fb95974d32093a0aa56bc682cfd68f776b3bd5210f0460414af7a

Tx prefix hash: 14270aff36d2e30399215ee28f3225e5de98a929f179a19012fdf33fbc37a3a1
Tx public key: fdeeadf0a99691c7440e1a7705758a87121c2673b4c7e1076044bdcabbc2e9fb
Timestamp: 1725608204 Timestamp [UCT]: 2024-09-06 07:36:44 Age [y:d:h:m:s]: 00:170:03:35:43
Block: 1104056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121401 RingCT/type: yes/0
Extra: 01fdeeadf0a99691c7440e1a7705758a87121c2673b4c7e1076044bdcabbc2e9fb021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a15a46d0b3b92cb79b544ae6c5eb2c1807ca4fe2a59f78b359536d0bb5d05cf 0.600000000000 1581115 of 15

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": 1104066, "vin": [ { "gen": { "height": 1104056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a15a46d0b3b92cb79b544ae6c5eb2c1807ca4fe2a59f78b359536d0bb5d05cf" } } ], "extra": [ 1, 253, 238, 173, 240, 169, 150, 145, 199, 68, 14, 26, 119, 5, 117, 138, 135, 18, 28, 38, 115, 180, 199, 225, 7, 96, 68, 189, 202, 187, 194, 233, 251, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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