Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd55ab7bd9add965d5ed6eb1328770a86c2fd4f362e55302687823bf42cdca78

Tx prefix hash: 8149effb10343f88190ba6f73269e55b7e0e4c2327d248d4b0a5f1985743a433
Tx public key: 4f1a91a5004819d6351bc7a43b62ea0cc4ff141ebaef64fe5f236b4f1701a051
Timestamp: 1705245558 Timestamp [UCT]: 2024-01-14 15:19:18 Age [y:d:h:m:s]: 01:300:10:50:17
Block: 935229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 473542 RingCT/type: yes/0
Extra: 014f1a91a5004819d6351bc7a43b62ea0cc4ff141ebaef64fe5f236b4f1701a0510211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 703054c6b2d9202d975f6d5d971336685fc50c13c103f88eef1070ce35e6efea 0.600000000000 1393245 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": 935239, "vin": [ { "gen": { "height": 935229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "703054c6b2d9202d975f6d5d971336685fc50c13c103f88eef1070ce35e6efea" } } ], "extra": [ 1, 79, 26, 145, 165, 0, 72, 25, 214, 53, 27, 199, 164, 59, 98, 234, 12, 196, 255, 20, 30, 186, 239, 100, 254, 95, 35, 107, 79, 23, 1, 160, 81, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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