Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 225f04aa23fb1f6266fe959a9707fb3f6041b2cbd1badcbc72a5d21d2ff2f9a4

Tx prefix hash: f5a4197397e879acda4b5ff522faa75714c9b173d57b4cf91b4c1d75603ca7e1
Tx public key: 32e9e2f4f33200b67623fdb392e3b18eb84eb8d2bad6aba5291da185b04d376b
Timestamp: 1682201946 Timestamp [UCT]: 2023-04-22 22:19:06 Age [y:d:h:m:s]: 01:130:12:00:39
Block: 744437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354684 RingCT/type: yes/0
Extra: 0132e9e2f4f33200b67623fdb392e3b18eb84eb8d2bad6aba5291da185b04d376b02110000000275e3f0e9000000000000000000

1 output(s) for total of 2.095904064000 dcy

stealth address amount amount idx
00: 37a6037b68589997cb164881f7e6de65955b36a1f183db16faa3ee6e2f7bb117 2.095904064000 1191756 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": 744447, "vin": [ { "gen": { "height": 744437 } } ], "vout": [ { "amount": 2095904064, "target": { "key": "37a6037b68589997cb164881f7e6de65955b36a1f183db16faa3ee6e2f7bb117" } } ], "extra": [ 1, 50, 233, 226, 244, 243, 50, 0, 182, 118, 35, 253, 179, 146, 227, 177, 142, 184, 78, 184, 210, 186, 214, 171, 165, 41, 29, 161, 133, 176, 77, 55, 107, 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