Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c10731c2475d400932e898f691cf51600850be6ac434b133d92c2b2f7ad2db6e

Tx prefix hash: 7020e98465b82b7ea3b3c2d8cb0db7e6a80d84982bf24bf234d5dc65d12f58bd
Tx public key: b2fff44391234aa18afead62a716ad3a604a797e5ccb203888654b3f3b6fed68
Timestamp: 1712517993 Timestamp [UCT]: 2024-04-07 19:26:33 Age [y:d:h:m:s]: 01:002:02:51:30
Block: 995491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262496 RingCT/type: yes/0
Extra: 01b2fff44391234aa18afead62a716ad3a604a797e5ccb203888654b3f3b6fed680211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba63e15af66613b22f53dff0e535f2cea3d9206c5510a11ae35200526fa418e5 0.600000000000 1455901 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": 995501, "vin": [ { "gen": { "height": 995491 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba63e15af66613b22f53dff0e535f2cea3d9206c5510a11ae35200526fa418e5" } } ], "extra": [ 1, 178, 255, 244, 67, 145, 35, 74, 161, 138, 254, 173, 98, 167, 22, 173, 58, 96, 74, 121, 126, 92, 203, 32, 56, 136, 101, 75, 63, 59, 111, 237, 104, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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