Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b91da722f0c1e2172838acd09d2e5a60f95699de7349c6f83fab37df1b613aa8

Tx prefix hash: a6788768979420463882511a7f94a2444ad43eec48a6e5d1ebdee3da14c9b3aa
Tx public key: f44c4bbef54a6ac13c489d61b6dcdcb2b14a6171a251681f8255507ed8876d5b
Timestamp: 1731875433 Timestamp [UCT]: 2024-11-17 20:30:33 Age [y:d:h:m:s]: 00:178:17:45:36
Block: 1155922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127588 RingCT/type: yes/0
Extra: 01f44c4bbef54a6ac13c489d61b6dcdcb2b14a6171a251681f8255507ed8876d5b021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2fd103ff63cbf731990d7c5779bb6d7a83a813b93b2545bb130391534ef5f4c 0.600000000000 1641541 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": 1155932, "vin": [ { "gen": { "height": 1155922 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2fd103ff63cbf731990d7c5779bb6d7a83a813b93b2545bb130391534ef5f4c" } } ], "extra": [ 1, 244, 76, 75, 190, 245, 74, 106, 193, 60, 72, 157, 97, 182, 220, 220, 178, 177, 74, 97, 113, 162, 81, 104, 31, 130, 85, 80, 126, 216, 135, 109, 91, 2, 17, 0, 0, 0, 3, 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