Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 028be8d36e8ebd60081f480f0fe4266a00564a45fedd93a4a2bb1c3d40270cdc

Tx prefix hash: e91b7d51216d778905bc1df2adec740db7261eb740cb6747e4d791176a4faedf
Tx public key: dc3ee2727de5925f4870be05c420b3486b00ee52b86e31e02eda349e0028d2de
Timestamp: 1577039046 Timestamp [UCT]: 2019-12-22 18:24:06 Age [y:d:h:m:s]: 04:342:12:06:49
Block: 29703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1133664 RingCT/type: yes/0
Extra: 01dc3ee2727de5925f4870be05c420b3486b00ee52b86e31e02eda349e0028d2de0211000000014ac5aa02000000000000000000

1 output(s) for total of 489.308199478000 dcy

stealth address amount amount idx
00: c0a2acbacc1908698c662ea9b3c26ad0594a1dc0ea6674829c24ea2d54bf6082 489.308199478000 48913 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": 29713, "vin": [ { "gen": { "height": 29703 } } ], "vout": [ { "amount": 489308199478, "target": { "key": "c0a2acbacc1908698c662ea9b3c26ad0594a1dc0ea6674829c24ea2d54bf6082" } } ], "extra": [ 1, 220, 62, 226, 114, 125, 229, 146, 95, 72, 112, 190, 5, 196, 32, 179, 72, 107, 0, 238, 82, 184, 110, 49, 224, 46, 218, 52, 158, 0, 40, 210, 222, 2, 17, 0, 0, 0, 1, 74, 197, 170, 2, 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