Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d8348545801432ae3ccaa78e97dd018b8ea1a72cdf005aadc66fa8c33501fe0

Tx prefix hash: a98f10f80d107dc32146664634193eee7665853b20ab3245a031bd458931903f
Tx public key: e9635be66b0b90807f84b6139d5433a019e48bdab3ff140dc53a3da8a413b307
Timestamp: 1578241311 Timestamp [UCT]: 2020-01-05 16:21:51 Age [y:d:h:m:s]: 05:059:17:29:13
Block: 39313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1192558 RingCT/type: yes/0
Extra: 01e9635be66b0b90807f84b6139d5433a019e48bdab3ff140dc53a3da8a413b30702110000017cdcee4b4d000000000000000000

1 output(s) for total of 454.716339373000 dcy

stealth address amount amount idx
00: e13c0f7c3a8680a6bfb43f186ff951676cf4e6b1f78e7f703b495c48a4d8efc7 454.716339373000 67699 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": 39323, "vin": [ { "gen": { "height": 39313 } } ], "vout": [ { "amount": 454716339373, "target": { "key": "e13c0f7c3a8680a6bfb43f186ff951676cf4e6b1f78e7f703b495c48a4d8efc7" } } ], "extra": [ 1, 233, 99, 91, 230, 107, 11, 144, 128, 127, 132, 182, 19, 157, 84, 51, 160, 25, 228, 139, 218, 179, 255, 20, 13, 197, 58, 61, 168, 164, 19, 179, 7, 2, 17, 0, 0, 1, 124, 220, 238, 75, 77, 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