Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85432e538e60ffbe5338480e516b69a8c2581c09455582ca651d226808725f5c

Tx prefix hash: 20eb3ef5a47de4e8cf5c1bdc4b95ecad3f7485431941dce3468e30c445785582
Tx public key: abc6a2eade97faa8b1ae63b5f9e9bb75063353b56631a9d3e302bbc0caababc7
Timestamp: 1675750783 Timestamp [UCT]: 2023-02-07 06:19:43 Age [y:d:h:m:s]: 01:274:04:17:27
Block: 691593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456869 RingCT/type: yes/0
Extra: 01abc6a2eade97faa8b1ae63b5f9e9bb75063353b56631a9d3e302bbc0caababc702110000000274b6d784000000000000000000

1 output(s) for total of 3.136643945000 dcy

stealth address amount amount idx
00: 45d89dd6f5ad8ff6a3e57b1c78b18919436e4c3d36dddb1cf55fba743fd1c8ed 3.136643945000 1134357 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": 691603, "vin": [ { "gen": { "height": 691593 } } ], "vout": [ { "amount": 3136643945, "target": { "key": "45d89dd6f5ad8ff6a3e57b1c78b18919436e4c3d36dddb1cf55fba743fd1c8ed" } } ], "extra": [ 1, 171, 198, 162, 234, 222, 151, 250, 168, 177, 174, 99, 181, 249, 233, 187, 117, 6, 51, 83, 181, 102, 49, 169, 211, 227, 2, 187, 192, 202, 171, 171, 199, 2, 17, 0, 0, 0, 2, 116, 182, 215, 132, 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