Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbc3e932763d6d97a0220f90d55be21b4736ae000f728ce06da5b4bace18d8e1

Tx prefix hash: 9dddf03583d3afe1a9320681c8b285400e87658f03927d17b09c9fdbdb84a573
Tx public key: 690e61ee2498a0739265a17946dbc11e4d3f74dbe893a80a9e17a6554fb7b79e
Timestamp: 1706827736 Timestamp [UCT]: 2024-02-01 22:48:56 Age [y:d:h:m:s]: 01:028:15:09:10
Block: 948346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281498 RingCT/type: yes/0
Extra: 01690e61ee2498a0739265a17946dbc11e4d3f74dbe893a80a9e17a6554fb7b79e02110000000d59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc3fd294414a4609bc86d5155fc2f8d868f9abc75a0921d19d1ef1ba2b6bafe3 0.600000000000 1406732 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": 948356, "vin": [ { "gen": { "height": 948346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc3fd294414a4609bc86d5155fc2f8d868f9abc75a0921d19d1ef1ba2b6bafe3" } } ], "extra": [ 1, 105, 14, 97, 238, 36, 152, 160, 115, 146, 101, 161, 121, 70, 219, 193, 30, 77, 63, 116, 219, 232, 147, 168, 10, 158, 23, 166, 85, 79, 183, 183, 158, 2, 17, 0, 0, 0, 13, 89, 218, 211, 245, 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