Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85b85007aaf2980e9fe38c17fb9dbfcc55666e4be5976cf245f762fa3ee286f8

Tx prefix hash: 760bc6a43e655cf3764c118b08cea622e1ec5cc689f3559bc8d72efce1545396
Tx public key: 42f84f5755cef3f17fc47b945a6f2abd59ed888f1115e86e685e19f19ca0174b
Timestamp: 1694869023 Timestamp [UCT]: 2023-09-16 12:57:03 Age [y:d:h:m:s]: 01:251:22:44:14
Block: 849396 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441191 RingCT/type: yes/0
Extra: 0142f84f5755cef3f17fc47b945a6f2abd59ed888f1115e86e685e19f19ca0174b021100000003faf35c9c000000000000000000

1 output(s) for total of 0.941019252000 dcy

stealth address amount amount idx
00: 5c8e1bad8ca0b49acbbb7849f9a01dcc255047a86470b35fb21edc0176d2b9bf 0.941019252000 1303060 of 0

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": 849406, "vin": [ { "gen": { "height": 849396 } } ], "vout": [ { "amount": 941019252, "target": { "key": "5c8e1bad8ca0b49acbbb7849f9a01dcc255047a86470b35fb21edc0176d2b9bf" } } ], "extra": [ 1, 66, 248, 79, 87, 85, 206, 243, 241, 127, 196, 123, 148, 90, 111, 42, 189, 89, 237, 136, 143, 17, 21, 232, 110, 104, 94, 25, 241, 156, 160, 23, 75, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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