Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1f15afc61aeab3696309d14ef027fc5a98a6b68432c5b5e6b24456fca6dfb53

Tx prefix hash: fc5ed27d754ebbd0b541350d99de93bb78bf669dfca43d17b5a23cee67f38b35
Tx public key: 7b21fce252317148277d158afe7faeff92b5beb481dedd0d5d9a9f1a201b3fe0
Timestamp: 1706792235 Timestamp [UCT]: 2024-02-01 12:57:15 Age [y:d:h:m:s]: 00:349:09:59:57
Block: 948041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250150 RingCT/type: yes/0
Extra: 017b21fce252317148277d158afe7faeff92b5beb481dedd0d5d9a9f1a201b3fe002110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f06a0b2477b65f08be40443ffee318f9f2d56ba40f3d6a1190d7fa17de679d4d 0.600000000000 1406411 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": 948051, "vin": [ { "gen": { "height": 948041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f06a0b2477b65f08be40443ffee318f9f2d56ba40f3d6a1190d7fa17de679d4d" } } ], "extra": [ 1, 123, 33, 252, 226, 82, 49, 113, 72, 39, 125, 21, 138, 254, 127, 174, 255, 146, 181, 190, 180, 129, 222, 221, 13, 93, 154, 159, 26, 32, 27, 63, 224, 2, 17, 0, 0, 0, 3, 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