Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3487720008e6dbc0407b6c09c3932f6025e60dfc4e5ea22cec1b5a1e0513a02a

Tx prefix hash: f7f58b9df475b5b4a367624073c89c4c058fadb9fd0106a75f1ea068d0d10ed0
Tx public key: a416e8b520dc3886da2eabd575ef4b977bb810f181599ddd65a26aff8457f066
Timestamp: 1646063744 Timestamp [UCT]: 2022-02-28 15:55:44 Age [y:d:h:m:s]: 02:302:00:58:06
Block: 448433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 735273 RingCT/type: yes/0
Extra: 01a416e8b520dc3886da2eabd575ef4b977bb810f181599ddd65a26aff8457f06602110000002ca8c141c5000000000000000000

1 output(s) for total of 20.051903166000 dcy

stealth address amount amount idx
00: 6cbe852f1f225b59f8f02f6c4f689e65304e66463d2aed5dbea016f86638c78f 20.051903166000 862810 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": 448443, "vin": [ { "gen": { "height": 448433 } } ], "vout": [ { "amount": 20051903166, "target": { "key": "6cbe852f1f225b59f8f02f6c4f689e65304e66463d2aed5dbea016f86638c78f" } } ], "extra": [ 1, 164, 22, 232, 181, 32, 220, 56, 134, 218, 46, 171, 213, 117, 239, 75, 151, 123, 184, 16, 241, 129, 89, 157, 221, 101, 162, 106, 255, 132, 87, 240, 102, 2, 17, 0, 0, 0, 44, 168, 193, 65, 197, 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