Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a80ea141cd181859df5077e78f4fd15c82c53d2a691710e2e961e03c1830882

Tx prefix hash: e989a22431a79844615ea6d6bf8affee5f1d2dc8c19b89ea955185a50bb66810
Tx public key: cd81ed35e5918df418e2d884c7d7dfa098766253b16b621de05256aae9ed73f8
Timestamp: 1716733061 Timestamp [UCT]: 2024-05-26 14:17:41 Age [y:d:h:m:s]: 00:300:01:40:12
Block: 1030484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214459 RingCT/type: yes/0
Extra: 01cd81ed35e5918df418e2d884c7d7dfa098766253b16b621de05256aae9ed73f802110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46bda2bb268a90415fc9535f2d4203ed9c79df2679de283c839ab4582e007da1 0.600000000000 1498739 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": 1030494, "vin": [ { "gen": { "height": 1030484 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46bda2bb268a90415fc9535f2d4203ed9c79df2679de283c839ab4582e007da1" } } ], "extra": [ 1, 205, 129, 237, 53, 229, 145, 141, 244, 24, 226, 216, 132, 199, 215, 223, 160, 152, 118, 98, 83, 177, 107, 98, 29, 224, 82, 86, 170, 233, 237, 115, 248, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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