Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b83a8f7661f9bcbaa6e078cf31a13f7e07e19f8db5bfb0eecf1b200b1ff615c3

Tx prefix hash: e60ed384d1d17578eec5399cac73aaf2a78bad0f0d7f57527356f95752fafdd9
Tx public key: f236cfae570afa4ace3a6a7bf3dc174dccdb738ff210e2b83242551172fa7cdb
Timestamp: 1732566545 Timestamp [UCT]: 2024-11-25 20:29:05 Age [y:d:h:m:s]: 00:143:21:42:48
Block: 1161636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102676 RingCT/type: yes/0
Extra: 01f236cfae570afa4ace3a6a7bf3dc174dccdb738ff210e2b83242551172fa7cdb021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c091e35d33ec4b8d7f010355b3d230206e0ff53e0c0394c49d720af3b7a4891 0.600000000000 1647291 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": 1161646, "vin": [ { "gen": { "height": 1161636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c091e35d33ec4b8d7f010355b3d230206e0ff53e0c0394c49d720af3b7a4891" } } ], "extra": [ 1, 242, 54, 207, 174, 87, 10, 250, 74, 206, 58, 106, 123, 243, 220, 23, 77, 204, 219, 115, 143, 242, 16, 226, 184, 50, 66, 85, 17, 114, 250, 124, 219, 2, 17, 0, 0, 0, 4, 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