Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21196c24236f8da991dfae6542abf806bf84a21b0f14e4bdaee1377663b60a7b

Tx prefix hash: 738282ee7e2838d26068d7a26a3bad85244ac2cd68e4c29e35658563693d4b85
Tx public key: a5a894a9b40e965ba3de227131d4c8e534645db2135aa171df943d0a058d13a5
Timestamp: 1762954801 Timestamp [UCT]: 2025-11-12 13:40:01 Age [y:d:h:m:s]: 00:041:08:22:34
Block: 1410553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29591 RingCT/type: yes/0
Extra: 01a5a894a9b40e965ba3de227131d4c8e534645db2135aa171df943d0a058d13a50211000000038368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a458c527c9250202122d20ac592b84a6760648d607eacb0cf441c7fa2ec8b1e1 0.600000000000 1899006 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": 1410563, "vin": [ { "gen": { "height": 1410553 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a458c527c9250202122d20ac592b84a6760648d607eacb0cf441c7fa2ec8b1e1" } } ], "extra": [ 1, 165, 168, 148, 169, 180, 14, 150, 91, 163, 222, 34, 113, 49, 212, 200, 229, 52, 100, 93, 178, 19, 90, 161, 113, 223, 148, 61, 10, 5, 141, 19, 165, 2, 17, 0, 0, 0, 3, 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