Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ded23ad6d7daece36ca3e727bb7fe1a2ce05e4e223301abd9a5891e895cf074d

Tx prefix hash: 815242026d2d393ab0e22016c9fd8bc904d56afa52aa44a63e7ebfc9439ad270
Tx public key: dff583adfb360eb645e50dadccf83cf68795b9d37c0c13606d28a5533dac93e7
Timestamp: 1574093492 Timestamp [UCT]: 2019-11-18 16:11:32 Age [y:d:h:m:s]: 05:008:20:14:05
Block: 11734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1149668 RingCT/type: yes/0
Extra: 01dff583adfb360eb645e50dadccf83cf68795b9d37c0c13606d28a5533dac93e7021100000003ccefb800000000000000000000

1 output(s) for total of 561.204669512000 dcy

stealth address amount amount idx
00: e1b9f9bff42e929df1a88ea0d8bd98dd7b6705dbc84b477c694f612d1a091d8e 561.204669512000 12813 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": 11744, "vin": [ { "gen": { "height": 11734 } } ], "vout": [ { "amount": 561204669512, "target": { "key": "e1b9f9bff42e929df1a88ea0d8bd98dd7b6705dbc84b477c694f612d1a091d8e" } } ], "extra": [ 1, 223, 245, 131, 173, 251, 54, 14, 182, 69, 229, 13, 173, 204, 248, 60, 246, 135, 149, 185, 211, 124, 12, 19, 96, 109, 40, 165, 83, 61, 172, 147, 231, 2, 17, 0, 0, 0, 3, 204, 239, 184, 0, 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