Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29cac3389d9f8ddc31f73531c954dd7238f1ccfae37d16bf9922e486236689b9

Tx prefix hash: 08d277c1c3e44d1d7500d137e1d9a45ce4f8fc9b8ad983ea295bb29e9ccaf50a
Tx public key: e5090dea3d2f9713a284a26eea4c6822b5b4e20ba8682ce348133b4f60d2c150
Timestamp: 1704675631 Timestamp [UCT]: 2024-01-08 01:00:31 Age [y:d:h:m:s]: 01:135:18:00:02
Block: 930485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358186 RingCT/type: yes/0
Extra: 01e5090dea3d2f9713a284a26eea4c6822b5b4e20ba8682ce348133b4f60d2c15002110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a9de32f0e8f6fb8c1df4b227c45486f71fbba2c99fb0fe71aeb3e65162c2acd 0.600000000000 1388367 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": 930495, "vin": [ { "gen": { "height": 930485 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a9de32f0e8f6fb8c1df4b227c45486f71fbba2c99fb0fe71aeb3e65162c2acd" } } ], "extra": [ 1, 229, 9, 13, 234, 61, 47, 151, 19, 162, 132, 162, 110, 234, 76, 104, 34, 181, 180, 226, 11, 168, 104, 44, 227, 72, 19, 59, 79, 96, 210, 193, 80, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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