Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e60e656ab2be3c9d696395a2e645a46a76a07f8c469022b9ead2fecdcdb9c77

Tx prefix hash: d06ba7a1e305f1bf352935bb5265a0cddcb8735900752a7e4ab91e9635db1a3e
Tx public key: 3b44573d2ece50f5c57cf5706010cc27987502d824fc3a2c903892c0a918aaad
Timestamp: 1763094906 Timestamp [UCT]: 2025-11-14 04:35:06 Age [y:d:h:m:s]: 00:050:06:10:10
Block: 1411710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35993 RingCT/type: yes/0
Extra: 013b44573d2ece50f5c57cf5706010cc27987502d824fc3a2c903892c0a918aaad0211000000082609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fb7d1093ec3bab4ec08e991ec078fba7f069dabc0d44dc1f701bb039a76c3ac 0.600000000000 1900173 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": 1411720, "vin": [ { "gen": { "height": 1411710 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fb7d1093ec3bab4ec08e991ec078fba7f069dabc0d44dc1f701bb039a76c3ac" } } ], "extra": [ 1, 59, 68, 87, 61, 46, 206, 80, 245, 197, 124, 245, 112, 96, 16, 204, 39, 152, 117, 2, 216, 36, 252, 58, 44, 144, 56, 146, 192, 169, 24, 170, 173, 2, 17, 0, 0, 0, 8, 38, 9, 179, 160, 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