Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03460087821e748986ea52f91a9c20a022d0d45d007ad894331ebd7383dcea5b

Tx prefix hash: 4d575a5e82b20efea6125710415fc60569d5514564ea669261bfa8efbfd95bee
Tx public key: c1ce4b90b411fd29d54b780de2a5af342c795454a9b1f89f4259975a96a065ac
Timestamp: 1739266774 Timestamp [UCT]: 2025-02-11 09:39:34 Age [y:d:h:m:s]: 00:328:13:19:05
Block: 1216845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232666 RingCT/type: yes/0
Extra: 01c1ce4b90b411fd29d54b780de2a5af342c795454a9b1f89f4259975a96a065ac021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cdfac7dcb116f0b4f721630963c3454b557de31f6bcf5db83e6e2d7567bf4826 0.600000000000 1703652 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": 1216855, "vin": [ { "gen": { "height": 1216845 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdfac7dcb116f0b4f721630963c3454b557de31f6bcf5db83e6e2d7567bf4826" } } ], "extra": [ 1, 193, 206, 75, 144, 180, 17, 253, 41, 213, 75, 120, 13, 226, 165, 175, 52, 44, 121, 84, 84, 169, 177, 248, 159, 66, 89, 151, 90, 150, 160, 101, 172, 2, 17, 0, 0, 0, 8, 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