Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35e32e532db09a963ff182a96fc1add35d20dcb4af4d4774abfba9793e1b91f7

Tx prefix hash: b6fae60aefde7d4d3d8cfbe533ff13bf9db42d7f9fc5cfe33590584bb484c74f
Tx public key: cb1737a83dbd60e58d082cf9e6eca6755858f06fc660e9e8ab9a774e5d758746
Timestamp: 1581244309 Timestamp [UCT]: 2020-02-09 10:31:49 Age [y:d:h:m:s]: 05:269:19:02:50
Block: 61236 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1343341 RingCT/type: yes/0
Extra: 01cb1737a83dbd60e58d082cf9e6eca6755858f06fc660e9e8ab9a774e5d758746021100000076026b59f3000000000000000000

1 output(s) for total of 384.680815672000 dcy

stealth address amount amount idx
00: 9a7603ea317a1a7dc3349fe7dd1bf4e3fc23968d9ba44cb6eb81b1ceaa3b77c9 384.680815672000 112846 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": 61246, "vin": [ { "gen": { "height": 61236 } } ], "vout": [ { "amount": 384680815672, "target": { "key": "9a7603ea317a1a7dc3349fe7dd1bf4e3fc23968d9ba44cb6eb81b1ceaa3b77c9" } } ], "extra": [ 1, 203, 23, 55, 168, 61, 189, 96, 229, 141, 8, 44, 249, 230, 236, 166, 117, 88, 88, 240, 111, 198, 96, 233, 232, 171, 154, 119, 78, 93, 117, 135, 70, 2, 17, 0, 0, 0, 118, 2, 107, 89, 243, 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