Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 808f17dc9c0edf3c606ba0e2bea0158e3d0d7409d802dc81daea9f7cf97b7a8e

Tx prefix hash: 865b1bf9fef4970ff8061bea1ff25489255578fd3ccbaf459a2df1a4b022ea68
Tx public key: 438e5b6b7abe54922f48e8382e13caa02c248c944758b7912aab1059c186ffbf
Timestamp: 1574549138 Timestamp [UCT]: 2019-11-23 22:45:38 Age [y:d:h:m:s]: 05:342:20:46:33
Block: 15974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1385451 RingCT/type: yes/0
Extra: 01438e5b6b7abe54922f48e8382e13caa02c248c944758b7912aab1059c186ffbf021100000009f95225a5000000000000000000

1 output(s) for total of 543.340889758000 dcy

stealth address amount amount idx
00: fc6646c344a894240f7835279e78d20da5c348bd10fe03f63773304b3d21b551 543.340889758000 21920 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": 15984, "vin": [ { "gen": { "height": 15974 } } ], "vout": [ { "amount": 543340889758, "target": { "key": "fc6646c344a894240f7835279e78d20da5c348bd10fe03f63773304b3d21b551" } } ], "extra": [ 1, 67, 142, 91, 107, 122, 190, 84, 146, 47, 72, 232, 56, 46, 19, 202, 160, 44, 36, 140, 148, 71, 88, 183, 145, 42, 171, 16, 89, 193, 134, 255, 191, 2, 17, 0, 0, 0, 9, 249, 82, 37, 165, 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