Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64c66f5968702aa071af1518aec75bc9796039da64a4d3a1d638852b6cffcd35

Tx prefix hash: 04f005812ef5833f6a0c333214dbdea46e1145e5c33b4d023da9452737faaf38
Tx public key: 0707a0550994074832e8329b4a4fb024a6ef6da6f88605facd81e33fd390e13d
Timestamp: 1707957952 Timestamp [UCT]: 2024-02-15 00:45:52 Age [y:d:h:m:s]: 01:263:05:49:14
Block: 957713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 446896 RingCT/type: yes/0
Extra: 010707a0550994074832e8329b4a4fb024a6ef6da6f88605facd81e33fd390e13d02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81701ad08640d8f08415ff46b0c318ae1a792d6c37d1c8dc4a41d9e08171e6c2 0.600000000000 1417062 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": 957723, "vin": [ { "gen": { "height": 957713 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81701ad08640d8f08415ff46b0c318ae1a792d6c37d1c8dc4a41d9e08171e6c2" } } ], "extra": [ 1, 7, 7, 160, 85, 9, 148, 7, 72, 50, 232, 50, 155, 74, 79, 176, 36, 166, 239, 109, 166, 248, 134, 5, 250, 205, 129, 227, 63, 211, 144, 225, 61, 2, 17, 0, 0, 0, 1, 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