Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5559941cba8b0ebaa28b49049e400738d99c6d3c8101d02edb2cc82f97ed6c7

Tx prefix hash: a0214da24234799a4dfa9db8e45a12f24f1574636ddd4b33489f1a8aec3a6807
Tx public key: 53a6f2200b55ce70d6164fb4a278e1675c1e262a5b8eaea3cff0ca15224848cc
Timestamp: 1729066097 Timestamp [UCT]: 2024-10-16 08:08:17 Age [y:d:h:m:s]: 00:220:21:18:28
Block: 1132731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157676 RingCT/type: yes/0
Extra: 0153a6f2200b55ce70d6164fb4a278e1675c1e262a5b8eaea3cff0ca15224848cc021100000013e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89ce4b3e8b029ae43e295c8f2c39dace5d535e2f38f95407a8fad4ef6d60c947 0.600000000000 1615714 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": 1132741, "vin": [ { "gen": { "height": 1132731 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89ce4b3e8b029ae43e295c8f2c39dace5d535e2f38f95407a8fad4ef6d60c947" } } ], "extra": [ 1, 83, 166, 242, 32, 11, 85, 206, 112, 214, 22, 79, 180, 162, 120, 225, 103, 92, 30, 38, 42, 91, 142, 174, 163, 207, 240, 202, 21, 34, 72, 72, 204, 2, 17, 0, 0, 0, 19, 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