Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f4d1b43d9db4dc5942aa5a15c3a7a728e94a6dfaae2d7f29961eceda93e82cb

Tx prefix hash: 670077e614658d98fa93b852c3cf8c4833fe814ed501fd723df97368e9036269
Tx public key: 34a2cdada45a0d64eab614949eddef31a7a1df3b3c66d1779ef8f5c54e63f962
Timestamp: 1718890958 Timestamp [UCT]: 2024-06-20 13:42:38 Age [y:d:h:m:s]: 00:311:23:48:52
Block: 1048364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222964 RingCT/type: yes/0
Extra: 0134a2cdada45a0d64eab614949eddef31a7a1df3b3c66d1779ef8f5c54e63f9620211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b14c05123f7fea20a2501905f2ee605cc87f4d404a094cc10b5be72ce2f280a0 0.600000000000 1518433 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": 1048374, "vin": [ { "gen": { "height": 1048364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b14c05123f7fea20a2501905f2ee605cc87f4d404a094cc10b5be72ce2f280a0" } } ], "extra": [ 1, 52, 162, 205, 173, 164, 90, 13, 100, 234, 182, 20, 148, 158, 221, 239, 49, 167, 161, 223, 59, 60, 102, 209, 119, 158, 248, 245, 197, 78, 99, 249, 98, 2, 17, 0, 0, 0, 8, 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