Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29a5375568f960d0494216d81986482f90a9fa5e5a52cf2620b57aeac31ce140

Tx prefix hash: c51fa9560fb056193a0e0f30ccafc2929eb9dce14552e86d051f316fecf1e278
Tx public key: 184ac26734e14e3fdd4525cb5c94d2f39aed9b9e816456293f2bc22c52d7ce78
Timestamp: 1717439306 Timestamp [UCT]: 2024-06-03 18:28:26 Age [y:d:h:m:s]: 00:143:17:53:45
Block: 1036332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102921 RingCT/type: yes/0
Extra: 01184ac26734e14e3fdd4525cb5c94d2f39aed9b9e816456293f2bc22c52d7ce780211000000010cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d9a90f3a7f384360557a1af9a4634817a38020e1fd93fd71c70f926a0e2d2d2 0.600000000000 1504857 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": 1036342, "vin": [ { "gen": { "height": 1036332 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d9a90f3a7f384360557a1af9a4634817a38020e1fd93fd71c70f926a0e2d2d2" } } ], "extra": [ 1, 24, 74, 194, 103, 52, 225, 78, 63, 221, 69, 37, 203, 92, 148, 210, 243, 154, 237, 155, 158, 129, 100, 86, 41, 63, 43, 194, 44, 82, 215, 206, 120, 2, 17, 0, 0, 0, 1, 12, 206, 6, 54, 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