Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa3d6fa628729f9b9adaeb72236b4ea04e6ef1ddbf3122b04e015438f9245490

Tx prefix hash: c7365176d513d485f9c5415aefba3fa419f4d008fda68e34d03567b223dd9eb7
Tx public key: ab74158a7bfa29a7476eb4156e371f520c3974a50bf3f8a4f24a2e3ca12d61ca
Timestamp: 1747552234 Timestamp [UCT]: 2025-05-18 07:10:34 Age [y:d:h:m:s]: 00:232:14:27:10
Block: 1285445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164021 RingCT/type: yes/0
Extra: 01ab74158a7bfa29a7476eb4156e371f520c3974a50bf3f8a4f24a2e3ca12d61ca0211000000031f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f44fb426f8e8d86d00eb23f64200ca991f7c833c92227fc1d6d2268fea611cf 0.600000000000 1772910 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": 1285455, "vin": [ { "gen": { "height": 1285445 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f44fb426f8e8d86d00eb23f64200ca991f7c833c92227fc1d6d2268fea611cf" } } ], "extra": [ 1, 171, 116, 21, 138, 123, 250, 41, 167, 71, 110, 180, 21, 110, 55, 31, 82, 12, 57, 116, 165, 11, 243, 248, 164, 242, 74, 46, 60, 161, 45, 97, 202, 2, 17, 0, 0, 0, 3, 31, 144, 81, 122, 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