Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30c2f40cc8760360c6dd4f7144ced80f2b2a6a97701ae6d109b31c1b762522c7

Tx prefix hash: 452ce72047b08f3bdb5e34d9c810d17f2b4844d0e3d0140dc81b194fb3910117
Tx public key: 919e5f10ebc191e39eaac1acb1b4e7a7d8d32d84276e263328e5db0a0adff997
Timestamp: 1725723692 Timestamp [UCT]: 2024-09-07 15:41:32 Age [y:d:h:m:s]: 00:222:19:45:00
Block: 1105013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159099 RingCT/type: yes/0
Extra: 01919e5f10ebc191e39eaac1acb1b4e7a7d8d32d84276e263328e5db0a0adff997021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59c46ab3f871fe35fc262aa1dbfce3da9cc4c040b07d67c1b541d2f156c13fd2 0.600000000000 1582350 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": 1105023, "vin": [ { "gen": { "height": 1105013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59c46ab3f871fe35fc262aa1dbfce3da9cc4c040b07d67c1b541d2f156c13fd2" } } ], "extra": [ 1, 145, 158, 95, 16, 235, 193, 145, 227, 158, 170, 193, 172, 177, 180, 231, 167, 216, 211, 45, 132, 39, 110, 38, 51, 40, 229, 219, 10, 10, 223, 249, 151, 2, 17, 0, 0, 0, 2, 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