Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49803dc477998869c90d00a925ddc5c16073e0c0737c89bc5871614b59534963

Tx prefix hash: 4c373a8d2f53274e9611591198933728c32e25071b20aa292c3f55c44b0c09f3
Tx public key: 6f4aac65a2faf2d0e7b398e3e38c4d0fa0fbada1a5c0280be7e9b9e8f9d35e37
Timestamp: 1734589437 Timestamp [UCT]: 2024-12-19 06:23:57 Age [y:d:h:m:s]: 00:103:04:23:29
Block: 1178423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73495 RingCT/type: yes/0
Extra: 016f4aac65a2faf2d0e7b398e3e38c4d0fa0fbada1a5c0280be7e9b9e8f9d35e37021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d76f446f9a073cfa1754452b1c960ab14d07a8205cefbf8258ff712d54a66e47 0.600000000000 1664810 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": 1178433, "vin": [ { "gen": { "height": 1178423 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d76f446f9a073cfa1754452b1c960ab14d07a8205cefbf8258ff712d54a66e47" } } ], "extra": [ 1, 111, 74, 172, 101, 162, 250, 242, 208, 231, 179, 152, 227, 227, 140, 77, 15, 160, 251, 173, 161, 165, 192, 40, 11, 231, 233, 185, 232, 249, 211, 94, 55, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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