Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 938550cfa9d12445f9cbe899b96fc3b5ed1af493ad93fd9b2eda4efe3fa8b6cc

Tx prefix hash: df359d67174a575b0d0224ad1f5c814b5063fcfe0e34eb5e0352ad029b7f88e0
Tx public key: 90f874ad6e6a5ff130cc114c54b13bb0cbaf45abd61710dffe8a84230c09e4d4
Timestamp: 1694011527 Timestamp [UCT]: 2023-09-06 14:45:27 Age [y:d:h:m:s]: 02:062:23:12:51
Block: 842279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 564691 RingCT/type: yes/0
Extra: 0190f874ad6e6a5ff130cc114c54b13bb0cbaf45abd61710dffe8a84230c09e4d4021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.993527962000 dcy

stealth address amount amount idx
00: 854a8dc3ae98904f50a91f57b24600acd9ecd0c71e0ae917b04f555762d129b3 0.993527962000 1295389 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": 842289, "vin": [ { "gen": { "height": 842279 } } ], "vout": [ { "amount": 993527962, "target": { "key": "854a8dc3ae98904f50a91f57b24600acd9ecd0c71e0ae917b04f555762d129b3" } } ], "extra": [ 1, 144, 248, 116, 173, 110, 106, 95, 241, 48, 204, 17, 76, 84, 177, 59, 176, 203, 175, 69, 171, 214, 23, 16, 223, 254, 138, 132, 35, 12, 9, 228, 212, 2, 17, 0, 0, 0, 6, 230, 210, 127, 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