Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d11950e95e28fb7f660e02f020d0a39c1f332fba92279e006e84ba6bc38b765

Tx prefix hash: e7d8ab127683795d6ee3db88ded76fa64b9b92e1c283738456d116c8ec974a47
Tx public key: f6271a3536e253670c9c1e8d83dfd4ab11b58bb44635f2f45dffa34a11e4da2a
Timestamp: 1749545334 Timestamp [UCT]: 2025-06-10 08:48:54 Age [y:d:h:m:s]: 00:152:22:48:45
Block: 1301951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106986 RingCT/type: yes/0
Extra: 01f6271a3536e253670c9c1e8d83dfd4ab11b58bb44635f2f45dffa34a11e4da2a02110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 245a4a3a40771fd104f5abe8138a8ca5c168ea509a691a331c24beb9aa4b505e 0.600000000000 1789516 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": 1301961, "vin": [ { "gen": { "height": 1301951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "245a4a3a40771fd104f5abe8138a8ca5c168ea509a691a331c24beb9aa4b505e" } } ], "extra": [ 1, 246, 39, 26, 53, 54, 226, 83, 103, 12, 156, 30, 141, 131, 223, 212, 171, 17, 181, 139, 180, 70, 53, 242, 244, 93, 255, 163, 74, 17, 228, 218, 42, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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