Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 724110c11b5da9464c70eb9384c217c233f6b472bf85d1113f06f44c2560822f

Tx prefix hash: cc8b220a4f2c88e28610ce72e5047d4dc5cb1036c61d8c8c428b07946baad102
Tx public key: 9487b79c76ddd2e39441e05cf8f0ee3ad6a7df4c4e5103507acf95bbce77a18c
Timestamp: 1704350885 Timestamp [UCT]: 2024-01-04 06:48:05 Age [y:d:h:m:s]: 01:153:21:41:10
Block: 927819 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371135 RingCT/type: yes/0
Extra: 019487b79c76ddd2e39441e05cf8f0ee3ad6a7df4c4e5103507acf95bbce77a18c0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d8584a4784471cd2f6d91e584217df1d1919564050cbc25ae820fb9978bed23 0.600000000000 1385655 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": 927829, "vin": [ { "gen": { "height": 927819 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d8584a4784471cd2f6d91e584217df1d1919564050cbc25ae820fb9978bed23" } } ], "extra": [ 1, 148, 135, 183, 156, 118, 221, 210, 227, 148, 65, 224, 92, 248, 240, 238, 58, 214, 167, 223, 76, 78, 81, 3, 80, 122, 207, 149, 187, 206, 119, 161, 140, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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