Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f1d4ead7c2d4af9d66ec0da34727911aac08f340b04a11728977c1f23f761a7

Tx prefix hash: 666241ce5ccff6ccc688667d0b2339fea79fb297a84851485ce267846d5899fc
Tx public key: 119561fd4c72881b3687f9d7aaeacd376b77cd3f98f0a216cd39819b44ec80bd
Timestamp: 1710299770 Timestamp [UCT]: 2024-03-13 03:16:10 Age [y:d:h:m:s]: 01:059:17:40:28
Block: 977150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303693 RingCT/type: yes/0
Extra: 01119561fd4c72881b3687f9d7aaeacd376b77cd3f98f0a216cd39819b44ec80bd02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 299120da6d59e10e1ead6d5f5dfe10fb46892509e1d037490c284d6db3b3bf5e 0.600000000000 1437151 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": 977160, "vin": [ { "gen": { "height": 977150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "299120da6d59e10e1ead6d5f5dfe10fb46892509e1d037490c284d6db3b3bf5e" } } ], "extra": [ 1, 17, 149, 97, 253, 76, 114, 136, 27, 54, 135, 249, 215, 170, 234, 205, 55, 107, 119, 205, 63, 152, 240, 162, 22, 205, 57, 129, 155, 68, 236, 128, 189, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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