Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c3a6ac7321b7f9fb9bb358cdc241dec808b21367868a2954a0312a0bee4afc5

Tx prefix hash: 5064bdbfea17d4c13c867f5f31dfbce3037ae7ce8dbf07c0a2e42332227d52f8
Tx public key: 7e92b11d0445e42413d71838a56456d561f8f66ab427eca83de6368d8ff8a06d
Timestamp: 1706801938 Timestamp [UCT]: 2024-02-01 15:38:58 Age [y:d:h:m:s]: 00:358:04:51:22
Block: 948121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256389 RingCT/type: yes/0
Extra: 017e92b11d0445e42413d71838a56456d561f8f66ab427eca83de6368d8ff8a06d02110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 204d598d75ce8bc7be50df2bdd396ac84fa7bc59ae25faf644d3c4d8ab8df8f9 0.600000000000 1406493 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": 948131, "vin": [ { "gen": { "height": 948121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "204d598d75ce8bc7be50df2bdd396ac84fa7bc59ae25faf644d3c4d8ab8df8f9" } } ], "extra": [ 1, 126, 146, 177, 29, 4, 69, 228, 36, 19, 215, 24, 56, 165, 100, 86, 213, 97, 248, 246, 106, 180, 39, 236, 168, 61, 230, 54, 141, 143, 248, 160, 109, 2, 17, 0, 0, 0, 10, 89, 218, 211, 245, 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