Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 708d709c95e75d0206492421e0d37a1dfcbf7898b5c100330761499b90c8a2b2

Tx prefix hash: 2533c0262898bf9705e6d6becb443c4a844f3c95603be89237475d1874b334ca
Tx public key: e8b5cf4926098fdb747ca0f7c86d21eafb765c20588b5e97cee303a5f84435ce
Timestamp: 1726056431 Timestamp [UCT]: 2024-09-11 12:07:11 Age [y:d:h:m:s]: 00:117:22:39:57
Block: 1107766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84345 RingCT/type: yes/0
Extra: 01e8b5cf4926098fdb747ca0f7c86d21eafb765c20588b5e97cee303a5f84435ce021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 343f076782a2b3ae2d8e7aa2defb38ee234916c122a4ab3cf1d84525b7e6c8a8 0.600000000000 1585419 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": 1107776, "vin": [ { "gen": { "height": 1107766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "343f076782a2b3ae2d8e7aa2defb38ee234916c122a4ab3cf1d84525b7e6c8a8" } } ], "extra": [ 1, 232, 181, 207, 73, 38, 9, 143, 219, 116, 124, 160, 247, 200, 109, 33, 234, 251, 118, 92, 32, 88, 139, 94, 151, 206, 227, 3, 165, 248, 68, 53, 206, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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