Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84ee12626323a14260fef35ebb3449f1bed8deb4396623064ba0b878633ff3ce

Tx prefix hash: 290f6ec70b7e4ecc5a4cee3ed03e8362c94dbb50a1a4be80ea7d73b1818741f2
Tx public key: 9ff786ccf3184e68895b2ad95c8867eb7b4aa9246eed52d2a74f5036d7d7f8d2
Timestamp: 1744764870 Timestamp [UCT]: 2025-04-16 00:54:30 Age [y:d:h:m:s]: 00:050:02:51:47
Block: 1262358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35867 RingCT/type: yes/0
Extra: 019ff786ccf3184e68895b2ad95c8867eb7b4aa9246eed52d2a74f5036d7d7f8d2021100000006dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0ae6fc3006bf979a7988a625e95c2b4a0c960d1748950fb7a46b7071ae32e11 0.600000000000 1749537 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": 1262368, "vin": [ { "gen": { "height": 1262358 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0ae6fc3006bf979a7988a625e95c2b4a0c960d1748950fb7a46b7071ae32e11" } } ], "extra": [ 1, 159, 247, 134, 204, 243, 24, 78, 104, 137, 91, 42, 217, 92, 136, 103, 235, 123, 74, 169, 36, 110, 237, 82, 210, 167, 79, 80, 54, 215, 215, 248, 210, 2, 17, 0, 0, 0, 6, 219, 181, 113, 193, 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