Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e3865925f37fd62a0c57fe08df4671e0b276765c1b54bc37fb7f09bf6519fbf

Tx prefix hash: c92715448d77d12836b2501b30ba544ab16e887d791844b1236483403282fb71
Tx public key: cda9d4a2a6138b007d1a9b28602342fea9bc79cab150e91f818efbb80b5d943e
Timestamp: 1726640508 Timestamp [UCT]: 2024-09-18 06:21:48 Age [y:d:h:m:s]: 00:113:21:19:51
Block: 1112601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81441 RingCT/type: yes/0
Extra: 01cda9d4a2a6138b007d1a9b28602342fea9bc79cab150e91f818efbb80b5d943e02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a370db0e9ce2ca5c3ccbf00e7e3d0d7071bcd36b09f1c6cd3185f12628cd769 0.600000000000 1591980 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": 1112611, "vin": [ { "gen": { "height": 1112601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a370db0e9ce2ca5c3ccbf00e7e3d0d7071bcd36b09f1c6cd3185f12628cd769" } } ], "extra": [ 1, 205, 169, 212, 162, 166, 19, 139, 0, 125, 26, 155, 40, 96, 35, 66, 254, 169, 188, 121, 202, 177, 80, 233, 31, 129, 142, 251, 184, 11, 93, 148, 62, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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