Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70ce4baa0497d34787b447c063337501b1f31b9c2486871b30c320ab604094c6

Tx prefix hash: 0b4bd837b71e1e6f180a4987d5df5eb805f0efd216216781dab4c8853afd10e3
Tx public key: e47e8c1eff0cb70e117672726782aa2016e8a65e629cfdf5aa54c52c85ebbf2d
Timestamp: 1736444157 Timestamp [UCT]: 2025-01-09 17:35:57 Age [y:d:h:m:s]: 00:160:12:31:17
Block: 1193746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114404 RingCT/type: yes/0
Extra: 01e47e8c1eff0cb70e117672726782aa2016e8a65e629cfdf5aa54c52c85ebbf2d0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e557ff830704d031c1875cfd0870c9a4f44bbb5a1f6ad0064edbf6aa892cbcd7 0.600000000000 1680311 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": 1193756, "vin": [ { "gen": { "height": 1193746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e557ff830704d031c1875cfd0870c9a4f44bbb5a1f6ad0064edbf6aa892cbcd7" } } ], "extra": [ 1, 228, 126, 140, 30, 255, 12, 183, 14, 17, 118, 114, 114, 103, 130, 170, 32, 22, 232, 166, 94, 98, 156, 253, 245, 170, 84, 197, 44, 133, 235, 191, 45, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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