Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1da9d52f6a511176591963f9c16b754a920c4100b97d9a8a0d47a83c70d5fd3

Tx prefix hash: 60bfa3c5d60ec3f796927282213f0ead2e6eb753b3d36f85e1a4372bd464b32a
Tx public key: 5deffd4adf41341661ebe9757654a526e7d67a27c297c349e14b4f1071f62f56
Timestamp: 1716391936 Timestamp [UCT]: 2024-05-22 15:32:16 Age [y:d:h:m:s]: 00:280:11:51:14
Block: 1027648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200443 RingCT/type: yes/0
Extra: 015deffd4adf41341661ebe9757654a526e7d67a27c297c349e14b4f1071f62f560211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0365e02a867a8c074bc11adcc6dd541e7161a6503e8ed6a28cd24c2fac48039 0.600000000000 1495379 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": 1027658, "vin": [ { "gen": { "height": 1027648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0365e02a867a8c074bc11adcc6dd541e7161a6503e8ed6a28cd24c2fac48039" } } ], "extra": [ 1, 93, 239, 253, 74, 223, 65, 52, 22, 97, 235, 233, 117, 118, 84, 165, 38, 231, 214, 122, 39, 194, 151, 195, 73, 225, 75, 79, 16, 113, 246, 47, 86, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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