Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b35750ede65acd8b95df0e161f56cc0549ef10f8788a21d9c06f8164ceb437ac

Tx prefix hash: de8af5c4ac918b07f629c43a4ae06ca416fd563ee26024101e19c0107d195e2e
Tx public key: 4d0a4b4e4f71b901430001a05d24156314590ec1591c3f68030a0f81865df125
Timestamp: 1587143627 Timestamp [UCT]: 2020-04-17 17:13:47 Age [y:d:h:m:s]: 04:166:09:04:33
Block: 93602 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1027480 RingCT/type: yes/0
Extra: 014d0a4b4e4f71b901430001a05d24156314590ec1591c3f68030a0f81865df125021100000ab186362411000000000000000000

1 output(s) for total of 300.509695354000 dcy

stealth address amount amount idx
00: 34f0ebe41c751de84e89f943720f4b415f5e748cf3295bf75c512c2d3d6689d0 300.509695354000 166650 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": 93612, "vin": [ { "gen": { "height": 93602 } } ], "vout": [ { "amount": 300509695354, "target": { "key": "34f0ebe41c751de84e89f943720f4b415f5e748cf3295bf75c512c2d3d6689d0" } } ], "extra": [ 1, 77, 10, 75, 78, 79, 113, 185, 1, 67, 0, 1, 160, 93, 36, 21, 99, 20, 89, 14, 193, 89, 28, 63, 104, 3, 10, 15, 129, 134, 93, 241, 37, 2, 17, 0, 0, 10, 177, 134, 54, 36, 17, 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