Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7df72fd6a522830c0deaae4deedda048830fdd79672a5c768851502924efa3e1

Tx prefix hash: 49582379f2f5e9b2cac3b14bb17d10f2d0c13177c0613002a486ddf700eaa929
Tx public key: ab9a1485295e841a4ad889965c9a16ed801db3f0ac015af4a04ba52f84aeeef6
Timestamp: 1672518275 Timestamp [UCT]: 2022-12-31 20:24:35 Age [y:d:h:m:s]: 01:336:22:03:21
Block: 664765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 501827 RingCT/type: yes/0
Extra: 01ab9a1485295e841a4ad889965c9a16ed801db3f0ac015af4a04ba52f84aeeef6021100000001e7ace25d000000000000000000

1 output(s) for total of 3.849085541000 dcy

stealth address amount amount idx
00: 7b139aa11a7cf6c1bf9dcca7f40b145b20254e4d6bc14a3356de0f985131f081 3.849085541000 1105772 of 0

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": 664775, "vin": [ { "gen": { "height": 664765 } } ], "vout": [ { "amount": 3849085541, "target": { "key": "7b139aa11a7cf6c1bf9dcca7f40b145b20254e4d6bc14a3356de0f985131f081" } } ], "extra": [ 1, 171, 154, 20, 133, 41, 94, 132, 26, 74, 216, 137, 150, 92, 154, 22, 237, 128, 29, 179, 240, 172, 1, 90, 244, 160, 75, 165, 47, 132, 174, 238, 246, 2, 17, 0, 0, 0, 1, 231, 172, 226, 93, 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