Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c42867f140c137964584a9caa13e15a77330f7db6e6dcd08309c589fd3eecf5

Tx prefix hash: d195c8d69f7bd42073f160189030b962cd2e3b06a2feea4fb576c9da21c30931
Tx public key: 91e5f86211281f51fc6e6d907cd925c774138cd17c648b1597f409fbd1b7edb4
Timestamp: 1696920853 Timestamp [UCT]: 2023-10-10 06:54:13 Age [y:d:h:m:s]: 01:217:21:33:31
Block: 866427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416784 RingCT/type: yes/0
Extra: 0191e5f86211281f51fc6e6d907cd925c774138cd17c648b1597f409fbd1b7edb4021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.826357001000 dcy

stealth address amount amount idx
00: ebe7760346473ab380cf2ce700e80b4494374187bd2dddf042e03b0f88f85abb 0.826357001000 1321019 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": 866437, "vin": [ { "gen": { "height": 866427 } } ], "vout": [ { "amount": 826357001, "target": { "key": "ebe7760346473ab380cf2ce700e80b4494374187bd2dddf042e03b0f88f85abb" } } ], "extra": [ 1, 145, 229, 248, 98, 17, 40, 31, 81, 252, 110, 109, 144, 124, 217, 37, 199, 116, 19, 140, 209, 124, 100, 139, 21, 151, 244, 9, 251, 209, 183, 237, 180, 2, 17, 0, 0, 0, 5, 230, 210, 127, 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