Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a05f0559f274643639be2f3e3dec7c7ed77654d8d3f6abd902eaad3fa2d958a

Tx prefix hash: 1fa6db9115d1592ccbe7d3020ea2329550f280fe144ecc00741e167dad477799
Tx public key: 8aca2ea7542f4accb4acd57f08591fef90f4dbb61db0cd5800cc33b4c9c4f114
Timestamp: 1738690416 Timestamp [UCT]: 2025-02-04 17:33:36 Age [y:d:h:m:s]: 00:334:18:10:02
Block: 1212070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237084 RingCT/type: yes/0
Extra: 018aca2ea7542f4accb4acd57f08591fef90f4dbb61db0cd5800cc33b4c9c4f114021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10b30d8b24d4078726c1a04bb727b6816d1f1d408f8e8546d0b652efb9cd3c18 0.600000000000 1698837 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": 1212080, "vin": [ { "gen": { "height": 1212070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10b30d8b24d4078726c1a04bb727b6816d1f1d408f8e8546d0b652efb9cd3c18" } } ], "extra": [ 1, 138, 202, 46, 167, 84, 47, 74, 204, 180, 172, 213, 127, 8, 89, 31, 239, 144, 244, 219, 182, 29, 176, 205, 88, 0, 204, 51, 180, 201, 196, 241, 20, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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