Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 667da7b1cb1e2359696a3f61133e4eb9cabcf9aee4b0ced72a3401eac3518abf

Tx prefix hash: 397c44c1d2a3992e33c60ce843ef2a703196537749caf3eb508e2bba802f47da
Tx public key: 0a2e612e3ac663846b3b6e15f01a31459d080541a19f0feace89a207d9a04f8b
Timestamp: 1753552519 Timestamp [UCT]: 2025-07-26 17:55:19 Age [y:d:h:m:s]: 00:025:01:26:47
Block: 1333946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16833 RingCT/type: yes/0
Extra: 010a2e612e3ac663846b3b6e15f01a31459d080541a19f0feace89a207d9a04f8b021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ee92c1cf4530779b15601a35dfb23bc8934555501687d418320b040d99bf72a 0.600000000000 1821745 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": 1333956, "vin": [ { "gen": { "height": 1333946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ee92c1cf4530779b15601a35dfb23bc8934555501687d418320b040d99bf72a" } } ], "extra": [ 1, 10, 46, 97, 46, 58, 198, 99, 132, 107, 59, 110, 21, 240, 26, 49, 69, 157, 8, 5, 65, 161, 159, 15, 234, 206, 137, 162, 7, 217, 160, 79, 139, 2, 17, 0, 0, 0, 2, 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