Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ca7b6b6c8b15c2ce5ef078a7d9973a269c6da3b1d569a40010118c7da84a6e3

Tx prefix hash: d13a244beb8cb32996fbc5443e2cbca0c4e5d0a1f59bcca2ad2f81102340b10c
Tx public key: f5fce93e3dc1980c843a1a4a07a248277967eb67cb229c3e256ce38c035b1bf5
Timestamp: 1728358358 Timestamp [UCT]: 2024-10-08 03:32:38 Age [y:d:h:m:s]: 00:203:14:39:57
Block: 1126847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145338 RingCT/type: yes/0
Extra: 01f5fce93e3dc1980c843a1a4a07a248277967eb67cb229c3e256ce38c035b1bf5021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d4dc4ddd37a47f479cc257544c0e7ead8bbd7922a0c3f26edd8cb597776229e 0.600000000000 1609642 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": 1126857, "vin": [ { "gen": { "height": 1126847 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d4dc4ddd37a47f479cc257544c0e7ead8bbd7922a0c3f26edd8cb597776229e" } } ], "extra": [ 1, 245, 252, 233, 62, 61, 193, 152, 12, 132, 58, 26, 74, 7, 162, 72, 39, 121, 103, 235, 103, 203, 34, 156, 62, 37, 108, 227, 140, 3, 91, 27, 245, 2, 17, 0, 0, 0, 8, 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