Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df2668002d565330f38089f83a78536eabcaf5f652986f3cd0fd8bcab4caf3a4

Tx prefix hash: aa1241d0f4ae3c7923955a2da978ddd521dc073943a9067bd3a3b7740fa144dd
Tx public key: 99b50d7be2a717dae405e638a04fa55ae1eb792c2e961a0edbb363f51c54fb5f
Timestamp: 1695497209 Timestamp [UCT]: 2023-09-23 19:26:49 Age [y:d:h:m:s]: 01:200:03:18:55
Block: 854609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404109 RingCT/type: yes/0
Extra: 0199b50d7be2a717dae405e638a04fa55ae1eb792c2e961a0edbb363f51c54fb5f021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.904327355000 dcy

stealth address amount amount idx
00: 0a47eb136af53a28ba8e6f8df8433e659df1ab30b5a2349f28c799327b0e8e54 0.904327355000 1308593 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": 854619, "vin": [ { "gen": { "height": 854609 } } ], "vout": [ { "amount": 904327355, "target": { "key": "0a47eb136af53a28ba8e6f8df8433e659df1ab30b5a2349f28c799327b0e8e54" } } ], "extra": [ 1, 153, 181, 13, 123, 226, 167, 23, 218, 228, 5, 230, 56, 160, 79, 165, 90, 225, 235, 121, 44, 46, 150, 26, 14, 219, 179, 99, 245, 28, 84, 251, 95, 2, 17, 0, 0, 0, 2, 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