Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ab726aca93ca0c360ad4d3ae5a544679a99692ea48ab5f668ead3f80fe04c69

Tx prefix hash: 5748dbbfd25c48dcf8771b0c2349db3375c991d28a86f9872b8ca528b5d20c13
Tx public key: 24a59a0d9d0ce065feaa23b1cabc7e60b636f91a0a7957e6da2c18cc41d37537
Timestamp: 1726915541 Timestamp [UCT]: 2024-09-21 10:45:41 Age [y:d:h:m:s]: 00:201:15:02:45
Block: 1114890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143922 RingCT/type: yes/0
Extra: 0124a59a0d9d0ce065feaa23b1cabc7e60b636f91a0a7957e6da2c18cc41d37537021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ab4b14ddf67bc358377bf9a0bc3fbc61867bb5aa36bb6f452d59641b428b839 0.600000000000 1594829 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": 1114900, "vin": [ { "gen": { "height": 1114890 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ab4b14ddf67bc358377bf9a0bc3fbc61867bb5aa36bb6f452d59641b428b839" } } ], "extra": [ 1, 36, 165, 154, 13, 157, 12, 224, 101, 254, 170, 35, 177, 202, 188, 126, 96, 182, 54, 249, 26, 10, 121, 87, 230, 218, 44, 24, 204, 65, 211, 117, 55, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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