Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35061e076359591600c62726d5662ffcabb4c1908e9ded625069a22c1eb7c5df

Tx prefix hash: c79d2d3114f0d7485cd316c67110ae4074ba9ad5666bf0d4e80eb28203aff1a0
Tx public key: 63fc0ea45e827da2e5d2d45a753f0724eb0f5b4d27fd1b105f5b41d43da06487
Timestamp: 1651249652 Timestamp [UCT]: 2022-04-29 16:27:32 Age [y:d:h:m:s]: 02:322:19:42:45
Block: 490762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 750502 RingCT/type: yes/0
Extra: 0163fc0ea45e827da2e5d2d45a753f0724eb0f5b4d27fd1b105f5b41d43da0648702110000000275e3f0e9000000000000000000

1 output(s) for total of 14.517839408000 dcy

stealth address amount amount idx
00: 6a8d8804d59a590aaf3d80aa5acd0e69aa115d746e416d3b8ad2fa0c5b2910b2 14.517839408000 913825 of 0

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": 490772, "vin": [ { "gen": { "height": 490762 } } ], "vout": [ { "amount": 14517839408, "target": { "key": "6a8d8804d59a590aaf3d80aa5acd0e69aa115d746e416d3b8ad2fa0c5b2910b2" } } ], "extra": [ 1, 99, 252, 14, 164, 94, 130, 125, 162, 229, 210, 212, 90, 117, 63, 7, 36, 235, 15, 91, 77, 39, 253, 27, 16, 95, 91, 65, 212, 61, 160, 100, 135, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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