Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6704fd65cdcf5b6e5f751498ba3241f8aced36943917f3d68599291f0b2f59a

Tx prefix hash: 40206315c4759eefe5e5d67464b767f6b2af27848614f139ac9ad19ad291485d
Tx public key: c1d181f214372c3d81a2514237d1885c194751a2ae5fc4f1f8fe39ea32160139
Timestamp: 1756320016 Timestamp [UCT]: 2025-08-27 18:40:16 Age [y:d:h:m:s]: 00:157:21:49:39
Block: 1355747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112701 RingCT/type: yes/0
Extra: 01c1d181f214372c3d81a2514237d1885c194751a2ae5fc4f1f8fe39ea32160139021100000002ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 571af614a198f941a34ae35aedf52606ed2f54c50f6aedf6e6f4ed4a85b69f0f 0.600000000000 1843750 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": 1355757, "vin": [ { "gen": { "height": 1355747 } } ], "vout": [ { "amount": 600000000, "target": { "key": "571af614a198f941a34ae35aedf52606ed2f54c50f6aedf6e6f4ed4a85b69f0f" } } ], "extra": [ 1, 193, 209, 129, 242, 20, 55, 44, 61, 129, 162, 81, 66, 55, 209, 136, 92, 25, 71, 81, 162, 174, 95, 196, 241, 248, 254, 57, 234, 50, 22, 1, 57, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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