Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0faea1b382382b113691a0b0fb2e481db80bb11682fe4d978c9faf87bee5ad6

Tx prefix hash: ddc663a2bd0e4de5caae0fa0686148ff51848fe2c09acc22f7d8db4e2ca07309
Tx public key: f78ec708306851cda8b24c8da1f591c07605900a22c3f6e36e27cfa403785dba
Timestamp: 1752722066 Timestamp [UCT]: 2025-07-17 03:14:26 Age [y:d:h:m:s]: 00:083:16:44:03
Block: 1327136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58530 RingCT/type: yes/0
Extra: 01f78ec708306851cda8b24c8da1f591c07605900a22c3f6e36e27cfa403785dba021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51b2d1f11eddf746bd0821835260789c403d493c2d4b930b809bb13f04f67ce4 0.600000000000 1814889 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": 1327146, "vin": [ { "gen": { "height": 1327136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51b2d1f11eddf746bd0821835260789c403d493c2d4b930b809bb13f04f67ce4" } } ], "extra": [ 1, 247, 142, 199, 8, 48, 104, 81, 205, 168, 178, 76, 141, 161, 245, 145, 192, 118, 5, 144, 10, 34, 195, 246, 227, 110, 39, 207, 164, 3, 120, 93, 186, 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