Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 423bddb6a1cde4f2cb6ca1bc180cd7f6036398a946ac6d2ca214500b40b03595

Tx prefix hash: 5576b9fc2a45fdaf61b0c87532d834e111e996c474d3d6ee77925d851470a63f
Tx public key: 666ecf3dd46e73026df5e1f283b29951245c22db5dd59ca07f31e47a0c998526
Timestamp: 1745398908 Timestamp [UCT]: 2025-04-23 09:01:48 Age [y:d:h:m:s]: 00:256:07:32:08
Block: 1267603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180995 RingCT/type: yes/0
Extra: 01666ecf3dd46e73026df5e1f283b29951245c22db5dd59ca07f31e47a0c998526021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2574cdffd255bd7ca8730a3186f8cbc61a3f7b53f7a090e6ce8dbf7fb00f4ca2 0.600000000000 1754832 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": 1267613, "vin": [ { "gen": { "height": 1267603 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2574cdffd255bd7ca8730a3186f8cbc61a3f7b53f7a090e6ce8dbf7fb00f4ca2" } } ], "extra": [ 1, 102, 110, 207, 61, 212, 110, 115, 2, 109, 245, 225, 242, 131, 178, 153, 81, 36, 92, 34, 219, 93, 213, 156, 160, 127, 49, 228, 122, 12, 153, 133, 38, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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