Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c35fd8d50353f5ab93893d667a0c213933e633f69ffc8b81787328d065e0956

Tx prefix hash: 4238b9a0fc24fe103c8dec08335618fa3d24bcb33e97eac68510d0a37420202d
Tx public key: 7e0d2a4aa9d56feaa7f8de8e9eb52af43b545de5e5427edd94c70ec3b283df2f
Timestamp: 1749490225 Timestamp [UCT]: 2025-06-09 17:30:25 Age [y:d:h:m:s]: 00:157:11:15:33
Block: 1301497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110215 RingCT/type: yes/0
Extra: 017e0d2a4aa9d56feaa7f8de8e9eb52af43b545de5e5427edd94c70ec3b283df2f021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87e2fc84fac574be3b24230c126df5a514783ac69420eb6b588c17567775930a 0.600000000000 1789056 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": 1301507, "vin": [ { "gen": { "height": 1301497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87e2fc84fac574be3b24230c126df5a514783ac69420eb6b588c17567775930a" } } ], "extra": [ 1, 126, 13, 42, 74, 169, 213, 111, 234, 167, 248, 222, 142, 158, 181, 42, 244, 59, 84, 93, 229, 229, 66, 126, 221, 148, 199, 14, 195, 178, 131, 223, 47, 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