Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53536814d2eb6dbbca2a3933fa24dcb380357e60799676f5927d958f15325ccb

Tx prefix hash: be7a41aa5229e2551233c032c2c9eb5612d796fbabad5ffd05180a91210d3bc8
Tx public key: 67e88761bcf8e9cc20f7fd8c88f4745ebfe52b02ebc151dc01a8f70ea4e40931
Timestamp: 1664409897 Timestamp [UCT]: 2022-09-29 00:04:57 Age [y:d:h:m:s]: 02:188:08:09:33
Block: 597822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 656174 RingCT/type: yes/0
Extra: 0167e88761bcf8e9cc20f7fd8c88f4745ebfe52b02ebc151dc01a8f70ea4e40931021100000001faf35c9c000000000000000000

1 output(s) for total of 6.414570893000 dcy

stealth address amount amount idx
00: f66a2ea2fdec15c3e4741ad02c558e24a73130127f1992f9acacdf28e5d657eb 6.414570893000 1033435 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": 597832, "vin": [ { "gen": { "height": 597822 } } ], "vout": [ { "amount": 6414570893, "target": { "key": "f66a2ea2fdec15c3e4741ad02c558e24a73130127f1992f9acacdf28e5d657eb" } } ], "extra": [ 1, 103, 232, 135, 97, 188, 248, 233, 204, 32, 247, 253, 140, 136, 244, 116, 94, 191, 229, 43, 2, 235, 193, 81, 220, 1, 168, 247, 14, 164, 228, 9, 49, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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