Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e859300df19277ee1e3ffeefd0fd386b2367a840c2f726a91b6dce9cfb4571d7

Tx prefix hash: bb5d45fd23dfb1b65fe1973236eb914e50f9a58a8de681bd5cc513b236de28d2
Tx public key: 4388ddb4ef8d804ba3ad3d763de84b5a119fc2b1aba00db75b17947f42bb848c
Timestamp: 1702395515 Timestamp [UCT]: 2023-12-12 15:38:35 Age [y:d:h:m:s]: 01:341:17:37:35
Block: 911625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 503089 RingCT/type: yes/0
Extra: 014388ddb4ef8d804ba3ad3d763de84b5a119fc2b1aba00db75b17947f42bb848c02110000000333af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca84742323c83bfe0e01a0008a1b159279df1317aa9b1d8898eb1e3eb4ce2207 0.600000000000 1368839 of 15

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": 911635, "vin": [ { "gen": { "height": 911625 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca84742323c83bfe0e01a0008a1b159279df1317aa9b1d8898eb1e3eb4ce2207" } } ], "extra": [ 1, 67, 136, 221, 180, 239, 141, 128, 75, 163, 173, 61, 118, 61, 232, 75, 90, 17, 159, 194, 177, 171, 160, 13, 183, 91, 23, 148, 127, 66, 187, 132, 140, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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