Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: deb24f2f23c2c86bdfea8165a727d9bf9be0e7397d9f97560edde0b0d52cea28

Tx prefix hash: 2e48306b5b24bf6203b55fc0864cc79b78a0b74af5d7a19e865e2ed84e249769
Tx public key: f1c4031fae8283036eaf63f9179dd98bb1cd0e858b569f96f56ddc5f4e9b78c8
Timestamp: 1717267511 Timestamp [UCT]: 2024-06-01 18:45:11 Age [y:d:h:m:s]: 00:315:01:48:09
Block: 1034910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225176 RingCT/type: yes/0
Extra: 01f1c4031fae8283036eaf63f9179dd98bb1cd0e858b569f96f56ddc5f4e9b78c80211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62b30fe607d10bcb288d6fe1506aae718954aaa910675cecbb2bfc4e2dfcc803 0.600000000000 1503429 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": 1034920, "vin": [ { "gen": { "height": 1034910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62b30fe607d10bcb288d6fe1506aae718954aaa910675cecbb2bfc4e2dfcc803" } } ], "extra": [ 1, 241, 196, 3, 31, 174, 130, 131, 3, 110, 175, 99, 249, 23, 157, 217, 139, 177, 205, 14, 133, 139, 86, 159, 150, 245, 109, 220, 95, 78, 155, 120, 200, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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