Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e9fa69ca72dd035ac97be90bced38ad8d1a43cc3dddc8a20ed5a2f8c3d15130

Tx prefix hash: ba6c7f9e6a294f488a61afcdb20d457c6e89d6a7a05322ae17318d7f944e116e
Tx public key: d2b18a859ad8717b2e932c5030939be0f8afaf1efd7fed531b691db0521b3fab
Timestamp: 1735904161 Timestamp [UCT]: 2025-01-03 11:36:01 Age [y:d:h:m:s]: 00:165:04:41:06
Block: 1189304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117756 RingCT/type: yes/0
Extra: 01d2b18a859ad8717b2e932c5030939be0f8afaf1efd7fed531b691db0521b3fab02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 461e02627f71beb9e9399b9dae3e3529114c61978675576cdcf935eb59417c60 0.600000000000 1675811 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": 1189314, "vin": [ { "gen": { "height": 1189304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "461e02627f71beb9e9399b9dae3e3529114c61978675576cdcf935eb59417c60" } } ], "extra": [ 1, 210, 177, 138, 133, 154, 216, 113, 123, 46, 147, 44, 80, 48, 147, 155, 224, 248, 175, 175, 30, 253, 127, 237, 83, 27, 105, 29, 176, 82, 27, 63, 171, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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