Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53b63bdb41cab574d518588eb752b247bd7db123a9d2a9f4aa16e3957136f903

Tx prefix hash: c5efe6586216b9b2fdf6b3b763bc6e5650e34ca4ecb4d56aaa5a5baf16ffd45a
Tx public key: 1b6f36a41030244bf335ed4040d1d3e0f5f873db2d2f1b8164f0a569cbadb973
Timestamp: 1707751277 Timestamp [UCT]: 2024-02-12 15:21:17 Age [y:d:h:m:s]: 01:123:21:05:17
Block: 956004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349523 RingCT/type: yes/0
Extra: 011b6f36a41030244bf335ed4040d1d3e0f5f873db2d2f1b8164f0a569cbadb973021100000001b6e2dc33000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 033ac04fdb9d990cb6b990484fcdc1cc9ed33ec58184560347ffc860b1a3a8f6 0.600000000000 1415306 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": 956014, "vin": [ { "gen": { "height": 956004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "033ac04fdb9d990cb6b990484fcdc1cc9ed33ec58184560347ffc860b1a3a8f6" } } ], "extra": [ 1, 27, 111, 54, 164, 16, 48, 36, 75, 243, 53, 237, 64, 64, 209, 211, 224, 245, 248, 115, 219, 45, 47, 27, 129, 100, 240, 165, 105, 203, 173, 185, 115, 2, 17, 0, 0, 0, 1, 182, 226, 220, 51, 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