Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9150a9d65f17fd4530d67a5944440af47c0c2049aa62a78a7cc81e9d448f896e

Tx prefix hash: 2a14bcd1e66497b9e5a4e3777ae68f726f5c4db5721442045ec48c9cf9383281
Tx public key: f834eb87fda280acfbe4f67648c3cfa4f2ad35403300296b38631d731d9c92f2
Timestamp: 1581946762 Timestamp [UCT]: 2020-02-17 13:39:22 Age [y:d:h:m:s]: 04:322:21:23:07
Block: 66683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123298 RingCT/type: yes/0
Extra: 01f834eb87fda280acfbe4f67648c3cfa4f2ad35403300296b38631d731d9c92f20211000000010aca7173000000000000000000

1 output(s) for total of 369.022076326000 dcy

stealth address amount amount idx
00: b72521a8a8f76f546a30518f7993c376b986254e8810f87c1d433bcda9e12019 369.022076326000 122846 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": 66693, "vin": [ { "gen": { "height": 66683 } } ], "vout": [ { "amount": 369022076326, "target": { "key": "b72521a8a8f76f546a30518f7993c376b986254e8810f87c1d433bcda9e12019" } } ], "extra": [ 1, 248, 52, 235, 135, 253, 162, 128, 172, 251, 228, 246, 118, 72, 195, 207, 164, 242, 173, 53, 64, 51, 0, 41, 107, 56, 99, 29, 115, 29, 156, 146, 242, 2, 17, 0, 0, 0, 1, 10, 202, 113, 115, 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