Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdf2c556df92b9b9a1b386f3ca2b7abd6446f867ab6d245d892821188992379b

Tx prefix hash: 46712a7d1cb52ab53b280091f0817e1ffc89b4f7ad5fcff9feb010a869d9aeca
Tx public key: 0a3a989801c436ebe4a27db3054f8260188a8c253677277d9c9955b063ad22d7
Timestamp: 1729825254 Timestamp [UCT]: 2024-10-25 03:00:54 Age [y:d:h:m:s]: 00:183:16:09:35
Block: 1138977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131093 RingCT/type: yes/0
Extra: 010a3a989801c436ebe4a27db3054f8260188a8c253677277d9c9955b063ad22d7021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f72b2d5201e5458af52ab87e8a511d5b64a6d9df482a6f7c400165ef58bdf863 0.600000000000 1622724 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": 1138987, "vin": [ { "gen": { "height": 1138977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f72b2d5201e5458af52ab87e8a511d5b64a6d9df482a6f7c400165ef58bdf863" } } ], "extra": [ 1, 10, 58, 152, 152, 1, 196, 54, 235, 228, 162, 125, 179, 5, 79, 130, 96, 24, 138, 140, 37, 54, 119, 39, 125, 156, 153, 85, 176, 99, 173, 34, 215, 2, 17, 0, 0, 0, 4, 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