Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45e4e62d02b0ac10a80ec4b0debc27b2c75707623cc522f0906f0380bf5f8d81

Tx prefix hash: 916a7fdae788b460763017fcf1c0324448f7a9dc7ced0a07becb9c5f08d9754e
Tx public key: 35f513eb20f4aaf1135b30628dcf8113e2bd9f22217311ede7979751cd6b9772
Timestamp: 1710206668 Timestamp [UCT]: 2024-03-12 01:24:28 Age [y:d:h:m:s]: 01:266:15:44:41
Block: 976376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449316 RingCT/type: yes/0
Extra: 0135f513eb20f4aaf1135b30628dcf8113e2bd9f22217311ede7979751cd6b97720211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bf17d0bb1d1424d8cbf82b6392dd9ce9d8f4543bd6f60db25ed6ba6fd4c2cf0 0.600000000000 1436369 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": 976386, "vin": [ { "gen": { "height": 976376 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bf17d0bb1d1424d8cbf82b6392dd9ce9d8f4543bd6f60db25ed6ba6fd4c2cf0" } } ], "extra": [ 1, 53, 245, 19, 235, 32, 244, 170, 241, 19, 91, 48, 98, 141, 207, 129, 19, 226, 189, 159, 34, 33, 115, 17, 237, 231, 151, 151, 81, 205, 107, 151, 114, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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