Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a351c85e9f0cfe55688a2f8533134ed4c27c4108c6111d9323450f3eb90b8597

Tx prefix hash: 7f39779d16cb9f86fb31599b6f820a7d784b6349c917e6c26c96efe06ce1650a
Tx public key: ae681320954a3fc195a31c4df68dc50608f9ae74f9a3cb741c5cecddd8cdc744
Timestamp: 1648374326 Timestamp [UCT]: 2022-03-27 09:45:26 Age [y:d:h:m:s]: 02:223:22:14:28
Block: 467393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 679566 RingCT/type: yes/0
Extra: 01ae681320954a3fc195a31c4df68dc50608f9ae74f9a3cb741c5cecddd8cdc74402110000000306faf294000000000000000000

1 output(s) for total of 17.351348004000 dcy

stealth address amount amount idx
00: 209758ba87731bb0006e7006f15492197065a2c9c1019870260cc0f6a8884910 17.351348004000 885886 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": 467403, "vin": [ { "gen": { "height": 467393 } } ], "vout": [ { "amount": 17351348004, "target": { "key": "209758ba87731bb0006e7006f15492197065a2c9c1019870260cc0f6a8884910" } } ], "extra": [ 1, 174, 104, 19, 32, 149, 74, 63, 193, 149, 163, 28, 77, 246, 141, 197, 6, 8, 249, 174, 116, 249, 163, 203, 116, 28, 92, 236, 221, 216, 205, 199, 68, 2, 17, 0, 0, 0, 3, 6, 250, 242, 148, 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