Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 804d163d515fe2b47385f0276a8f4f14d0e57ca82a05497acd6cd12f71c7a92c

Tx prefix hash: 90e81936c21d55d541c5bd801b3f7d436665adf34ae1e1e8839ae6fe1390c763
Tx public key: 26aeb8414742769b9d259aa18dac11fa44b480b775b1c96bfa93a92388063f53
Timestamp: 1750959202 Timestamp [UCT]: 2025-06-26 17:33:22 Age [y:d:h:m:s]: 00:142:10:57:43
Block: 1313320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99819 RingCT/type: yes/0
Extra: 0126aeb8414742769b9d259aa18dac11fa44b480b775b1c96bfa93a92388063f530211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd7f9a2fe76a6d57f2ed4721d7ec5ed0533e0b5644d0550342f543e4b2982de1 0.600000000000 1800959 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": 1313330, "vin": [ { "gen": { "height": 1313320 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd7f9a2fe76a6d57f2ed4721d7ec5ed0533e0b5644d0550342f543e4b2982de1" } } ], "extra": [ 1, 38, 174, 184, 65, 71, 66, 118, 155, 157, 37, 154, 161, 141, 172, 17, 250, 68, 180, 128, 183, 117, 177, 201, 107, 250, 147, 169, 35, 136, 6, 63, 83, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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