Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5940cd52568a35e55be1c832cd5ef0492a00177d89c431a9a7d189ff608afa42

Tx prefix hash: f1495f354264ca801f21dee478514b8c4d8826928dd844770d3fd0c7477fdcdc
Tx public key: 3e4981ac395cbfb2b4d92c09c4e4b24e3f7c22fbc729e826fbe19818f31d63e6
Timestamp: 1729046895 Timestamp [UCT]: 2024-10-16 02:48:15 Age [y:d:h:m:s]: 00:193:10:27:34
Block: 1132578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138029 RingCT/type: yes/0
Extra: 013e4981ac395cbfb2b4d92c09c4e4b24e3f7c22fbc729e826fbe19818f31d63e60211000000053cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b723d75301b2413ea3755291000fbc252d7519c89e504b7049bb5ee767389a6 0.600000000000 1615527 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": 1132588, "vin": [ { "gen": { "height": 1132578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b723d75301b2413ea3755291000fbc252d7519c89e504b7049bb5ee767389a6" } } ], "extra": [ 1, 62, 73, 129, 172, 57, 92, 191, 178, 180, 217, 44, 9, 196, 228, 178, 78, 63, 124, 34, 251, 199, 41, 232, 38, 251, 225, 152, 24, 243, 29, 99, 230, 2, 17, 0, 0, 0, 5, 60, 208, 252, 6, 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