Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8c43ee328c8a22fc1ee457fcd69d6beb92f8e64b0b1a9ee5ed572f6c6a50d00

Tx prefix hash: 4340865076f03376382eaeefd412355c38890963bce599d8ed4bbbbb11c3490c
Tx public key: c0b1e93ed3732ded35f73a6c0f9004798c23cc734d2a74ca62a7ae24c235b475
Timestamp: 1717499816 Timestamp [UCT]: 2024-06-04 11:16:56 Age [y:d:h:m:s]: 00:359:07:23:01
Block: 1036838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256825 RingCT/type: yes/0
Extra: 01c0b1e93ed3732ded35f73a6c0f9004798c23cc734d2a74ca62a7ae24c235b47502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99350cf956e24ff3bbab46724a6b7bc69a8939f90397339ae599f67631f23fcf 0.600000000000 1505367 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": 1036848, "vin": [ { "gen": { "height": 1036838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99350cf956e24ff3bbab46724a6b7bc69a8939f90397339ae599f67631f23fcf" } } ], "extra": [ 1, 192, 177, 233, 62, 211, 115, 45, 237, 53, 247, 58, 108, 15, 144, 4, 121, 140, 35, 204, 115, 77, 42, 116, 202, 98, 167, 174, 36, 194, 53, 180, 117, 2, 17, 0, 0, 0, 1, 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