Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36e314356cdbcdbe1a37732912f5e5999a261cdd26d2faaa95fc08f86500a86a

Tx prefix hash: 5849d4f5e8700fdd2750260c3231bfbcad1983ef87933b3cc581a7fcff5b5d3d
Tx public key: 9cd0d0706fa6f70762e0bb43bbcff70d251d826f46a1d6db2cd17f524806eb37
Timestamp: 1721068961 Timestamp [UCT]: 2024-07-15 18:42:41 Age [y:d:h:m:s]: 00:253:11:36:45
Block: 1066435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181053 RingCT/type: yes/0
Extra: 019cd0d0706fa6f70762e0bb43bbcff70d251d826f46a1d6db2cd17f524806eb3702110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9eddf962d69ffe329f5077a788216f5f0a7338b0d530e2c643fcc1c5f7a6b202 0.600000000000 1537030 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": 1066445, "vin": [ { "gen": { "height": 1066435 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9eddf962d69ffe329f5077a788216f5f0a7338b0d530e2c643fcc1c5f7a6b202" } } ], "extra": [ 1, 156, 208, 208, 112, 111, 166, 247, 7, 98, 224, 187, 67, 187, 207, 247, 13, 37, 29, 130, 111, 70, 161, 214, 219, 44, 209, 127, 82, 72, 6, 235, 55, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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