Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 117b0d96e1705c043fd26072f59aba4e811862c4ab27b3224d07a475d13bb008

Tx prefix hash: 7a0d0f5a78b0ab4981d33234b7695f229cb2b3eadced17a287f7f06260588ebe
Tx public key: 78d13ffbffcef5c231348a5b493b6bff8b52010c0fc2a1cf93b09adfe9c5c25b
Timestamp: 1765897282 Timestamp [UCT]: 2025-12-16 15:01:22 Age [y:d:h:m:s]: 00:004:19:09:36
Block: 1434922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3440 RingCT/type: yes/0
Extra: 0178d13ffbffcef5c231348a5b493b6bff8b52010c0fc2a1cf93b09adfe9c5c25b02110000000370609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 820b36114602e1d9a8cd9397d50cbd85271c2cba01349d3ae4c928d7b7922717 0.600000000000 1923719 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": 1434932, "vin": [ { "gen": { "height": 1434922 } } ], "vout": [ { "amount": 600000000, "target": { "key": "820b36114602e1d9a8cd9397d50cbd85271c2cba01349d3ae4c928d7b7922717" } } ], "extra": [ 1, 120, 209, 63, 251, 255, 206, 245, 194, 49, 52, 138, 91, 73, 59, 107, 255, 139, 82, 1, 12, 15, 194, 161, 207, 147, 176, 154, 223, 233, 197, 194, 91, 2, 17, 0, 0, 0, 3, 112, 96, 157, 3, 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