Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46585e5d5f1264513ce83d2c55999891c7967c1793ed724f4cc1e847a050c63d

Tx prefix hash: 6044baa45b1b08a8bf28c5e89b3bd2bc9d1c3aa79151acd47f3d53786e58e96a
Tx public key: 089bdd3e99afbe1692332d4d102e129de85ce77fd7b88e87aa1a0bcec3836bc3
Timestamp: 1715394998 Timestamp [UCT]: 2024-05-11 02:36:38 Age [y:d:h:m:s]: 01:205:15:30:15
Block: 1019400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405602 RingCT/type: yes/0
Extra: 01089bdd3e99afbe1692332d4d102e129de85ce77fd7b88e87aa1a0bcec3836bc302110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f42ecf34a4b5c8870b96fc743f6911d285166c4db1f60c513765bf01570e586 0.600000000000 1483357 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": 1019410, "vin": [ { "gen": { "height": 1019400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f42ecf34a4b5c8870b96fc743f6911d285166c4db1f60c513765bf01570e586" } } ], "extra": [ 1, 8, 155, 221, 62, 153, 175, 190, 22, 146, 51, 45, 77, 16, 46, 18, 157, 232, 92, 231, 127, 215, 184, 142, 135, 170, 26, 11, 206, 195, 131, 107, 195, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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