Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 154562d5d1223fcc06c78d1b4805f9f8feb3714eb5e4bd10d5cf75b230b27f15

Tx prefix hash: c2d749807a566b5797fae8674de43d9f9a0d98a2e44ab7a8151b2f6878aeca30
Tx public key: 131786760ab3fbbd86b6a84236b692f0a457af9ef24d82f8dfcd7bc71ad48854
Timestamp: 1717195733 Timestamp [UCT]: 2024-05-31 22:48:53 Age [y:d:h:m:s]: 00:298:14:13:45
Block: 1034308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213383 RingCT/type: yes/0
Extra: 01131786760ab3fbbd86b6a84236b692f0a457af9ef24d82f8dfcd7bc71ad4885402110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d892e60eceae5d3ecffc131a8a5e61148f48e6e6aff21bf1c1fc262f93447cc 0.600000000000 1502809 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": 1034318, "vin": [ { "gen": { "height": 1034308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d892e60eceae5d3ecffc131a8a5e61148f48e6e6aff21bf1c1fc262f93447cc" } } ], "extra": [ 1, 19, 23, 134, 118, 10, 179, 251, 189, 134, 182, 168, 66, 54, 182, 146, 240, 164, 87, 175, 158, 242, 77, 130, 248, 223, 205, 123, 199, 26, 212, 136, 84, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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