Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0df390a70c7ddacc2a23d67d8e0634c13263bb29e317e110f0675ca7d8da7e2d

Tx prefix hash: 61d58ba9af35c92683e49857e220e4344f6f7965b1317bda7a2cc1006f30ba7f
Tx public key: 23abe15eadf508c88189234c109b3b268e5bef4e93de8971a4d6022450d2e0ae
Timestamp: 1725172280 Timestamp [UCT]: 2024-09-01 06:31:20 Age [y:d:h:m:s]: 00:215:01:46:14
Block: 1100436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153563 RingCT/type: yes/0
Extra: 0123abe15eadf508c88189234c109b3b268e5bef4e93de8971a4d6022450d2e0ae02110000000323a894fd000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f749c6e90ede25e7089889d062a9b6f2214f6fd93289acce795a9923e1c0615 0.600000000000 1576415 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": 1100446, "vin": [ { "gen": { "height": 1100436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f749c6e90ede25e7089889d062a9b6f2214f6fd93289acce795a9923e1c0615" } } ], "extra": [ 1, 35, 171, 225, 94, 173, 245, 8, 200, 129, 137, 35, 76, 16, 155, 59, 38, 142, 91, 239, 78, 147, 222, 137, 113, 164, 214, 2, 36, 80, 210, 224, 174, 2, 17, 0, 0, 0, 3, 35, 168, 148, 253, 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