Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f091c399052d2ab4ca866515ca9a906dab8c03c833cf5d285ae4e65f9d5da5c7

Tx prefix hash: 739f202a0dab2355d68523274ca82a7acb54a0cd01df47373950620f16523bea
Tx public key: 5d17dc8e74c058d40df137edd68c284308a253083ba5a9fcfa1aa9126dee53b3
Timestamp: 1577815028 Timestamp [UCT]: 2019-12-31 17:57:08 Age [y:d:h:m:s]: 04:363:14:56:27
Block: 35925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1148978 RingCT/type: yes/0
Extra: 015d17dc8e74c058d40df137edd68c284308a253083ba5a9fcfa1aa9126dee53b30211000000b0c3a1a09f000000000000000000

1 output(s) for total of 466.623294316000 dcy

stealth address amount amount idx
00: 7a4aeb530ee967b47c09df21bd06d64f43a2a56d36d9b877e4c48b80e579f9b4 466.623294316000 60683 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": 35935, "vin": [ { "gen": { "height": 35925 } } ], "vout": [ { "amount": 466623294316, "target": { "key": "7a4aeb530ee967b47c09df21bd06d64f43a2a56d36d9b877e4c48b80e579f9b4" } } ], "extra": [ 1, 93, 23, 220, 142, 116, 192, 88, 212, 13, 241, 55, 237, 214, 140, 40, 67, 8, 162, 83, 8, 59, 165, 169, 252, 250, 26, 169, 18, 109, 238, 83, 179, 2, 17, 0, 0, 0, 176, 195, 161, 160, 159, 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