Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cba8f3b3ca4de3a5545e56c6af2ccf0a687edb86add1d99b4d006c95a67a4dd

Tx prefix hash: b59be3467ecbcbdfae90e788544c837764db17f1f6435400e87aa3c5a4019d5c
Tx public key: dee3259a08da21536f4a118e45bf2963b83c52c15f78ca23c25acaa784d6b3af
Timestamp: 1748190012 Timestamp [UCT]: 2025-05-25 16:20:12 Age [y:d:h:m:s]: 00:222:13:01:12
Block: 1290737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156802 RingCT/type: yes/0
Extra: 01dee3259a08da21536f4a118e45bf2963b83c52c15f78ca23c25acaa784d6b3af0211000000041f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c87f700d37f4b7b92d8914794e5d13d1607b29c26ab1fd3e7c7bdec49a1c46e 0.600000000000 1778208 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": 1290747, "vin": [ { "gen": { "height": 1290737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c87f700d37f4b7b92d8914794e5d13d1607b29c26ab1fd3e7c7bdec49a1c46e" } } ], "extra": [ 1, 222, 227, 37, 154, 8, 218, 33, 83, 111, 74, 17, 142, 69, 191, 41, 99, 184, 60, 82, 193, 95, 120, 202, 35, 194, 90, 202, 167, 132, 214, 179, 175, 2, 17, 0, 0, 0, 4, 31, 144, 81, 122, 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